<?php
/**
 * <https://y.st./>
 * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'Backing up keys',
	'<{body}>' => <<<END
<p>
	<strong>*This part of today&apos;s weblog entry was withheld until {$entry(2015, 11, 6)}.*</strong>
</p>
<blockquote>
<p>
	I figured out what domain name I want to use for purposes that do not need to be fully disconnected from me, but that it needs to be known that they are not specifically my hosts.
	This would include an email server for delegating email addresses to people that ask me for them.
	(I don&apos;t know why people want an email address at my domain, but several people have asked for one.) This would also include subdomains granted to people who want them, should that desire arise.
	But most importantly, this would include works I start but would like to become collaborative.
	Collaborative works do not belong directly in Yst Domain, but I do not want to completely distance myself from them.
</p>
<p>
	At first, I looked into getting <code>//why.st.</code>, a pun on my main name.
	However, <code>//why.st.</code> has already been purchased.
	Unfortunately, the name is not in any real use, and is just being parked on an advertisement page.
	It is available for sale, but it costs \$3500 $a[USD], which is more than it would cost to get ahold of the more valuable <code>//q.st.</code> or <code>//z.st.</code>, both of which are still available.
	I decided to see if I could fine a more obscure homonym.
	What I found quite surprised me.
	Both &quot;wye&quot; and &quot;wy&quot;, seemingly the only English homonyms of &quot;why&quot;, literally refer to the letter &quot;y&quot;.
	They are the spelled out names of this letter.
	I had looked for the <a href="https://en.wikipedia.org/wiki/English_alphabet#Letter_names">spelling of the English letters</a> in the past but could not find them, concluding that there was no spelling of the letter names.
	Both <code>//wy.st.</code> and <code>//wye.st.</code> are available, with the former being substantially more expensive as the registry charges more for the initial registration of second-level labels consisting of less than three characters.
</p>
<p>
	Looking into the Wikipidia article on the letter wye, I found its purpose in old English words such as &quot;ye&quot;.
	It seems that old typefaces did not contain the letter thorn, which was still in use at the time, so <a href="https://en.wikipedia.org/wiki/Y#Confusion_in_writing_with_the_letter_thorn">wye was used instead</a>.
	In old words such as &quot;ye&quot;, the wye is pronounced like the modern tee aitch, not like the modern wye.
	so &quot;ye&quot; is pronounced as &quot;the&quot;, the same as the modern word is pronounced today.
	Thorn would be another, and probably better, name for use as an entity that I am associated with, but is not truly or not fully me.
	It could be spelled as <code>//thorn.st.</code> or as <code>//xn--vda.st.</code>.
	Using the former, spelling of the domain becomes much more clear than that of <code>//wye.st.</code>.
	&quot;Wye dot ess tee&quot; sounds too much like my personal domain, <code>//y.st.</code>, but &quot;thorn dot ess tee&quot; should let people know that the domain is <code>//thorn.st</code>.
	It is also further from my name even when the spelling is known, making it less about me.
</p>
<p>
	I had planned on eventually setting up a website using the domain <code>//notanumber.st.</code>, making the website about our need to escape being identified casually by numbers instead of names.
	I wanted to try to build on this enough to create a small, active community around it.
	However, I think I will instead try to build a community around the name Thorn, who will stand for three important virtues: freedom, such as the freedom to derive and modify, privacy, the need to not be under a microscope at all times, and individuality, such knowing that you are worth having a name and should never casually identify by number.
	I will try building software under the group name Thorn and see if anyone interested comes along to work with me.
</p>
<p>
	I cannot post this part of today&apos;s weblog entry yet though.
	I&apos;m not yet buying the domain and do not want it taken out from under me, at least not due to what I&apos;ve posted here.
	Both to give myself time to think on the name and to align my payment due dates, I&apos;ll wait until <a href="https:/en/weblog/2016/03-March/07.xhtml">March Seven</a> to make the purchase.
</p>
</blockquote>
<p>
	I went into the big box store today to ask about their website&apos;s lack of job openings in our area despite the &quot;help wanted&quot; signs posted outside.
	As I had feared, instead of actually having any information on the issue, the customer service representative instructed me to use one of the computers in the back to apply.
	These computers ask you to either log in with current login credentials or create new login credentials.
	Not being at my own machine, I cannot use my encrypted password data base and paste the password.
	I decided to suck it up and try using a hand-typed password generated with KeePassDroid, but that only got me so far.
	The next step required that I answer no less than five &quot;security&quot; questions.
	Without my password database, answering those in a secure way was more than I was up for.
	I left without finishing the application.
</p>
<p>
	I stopped in a restaurant on the way home that I had seen also had job openings available.
	Before I could ask about them, I saw the stack of papers on the counter, each with instructions for applying online.
	I took one and headed home.
	I will fill out the application online tomorrow probably.
</p>
<p>
	<a href="https://wowana.me/">Wowaname</a> suggested to me that I removed my password from my account on <a href="ircs://irc.volatile.ch:6697/">Volatile</a>, a new feature that she coded today or yesterday.
	Doing so requires having authentication via client certificate set up, which I have already done.
	However, this means that if I somehow lose my client certificate and not my KeePassX database, I&apos;ll have just locked myself out of my account.
	It is a more secure option though, so I copied my client certificate into my KeePassX database.
	If I ever lose that database, I&apos;ll lose more than just an $a[IRC] account, so it is safe to say that at that point, a lost $a[IRC] account will be the last of my worries.
	I have been trying to figure out how to back that database up somewhere that I can access without proving that I am me while not exposing it to a maraud of potential attackers.
	I haven&apos;t thought of any usable ideas yet, but I&apos;ll keep trying and keep the database backed up both to my mobile and my external hard drive.
</p>
<p>
	While I was at it, I also copied my $a[SSH] keypair into the KeePassX database and moved my other $a[TLS] keypairs and onion keys into the database.
	I didn&apos;t move every last onion key I have into the database, but I moved all that were generated as permutations of <code>//y.st.</code> or <code>//ystyst.mp.</code>.
	Speaking of that, I found an onion permutation of <code>//ystyst.mp.</code> in my new onion keys directory.
	It must have been generated without my noticing one time that I ran the onion key generation script for a short while.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
END
);
